Unstructured Footnotes in Electronic Mortgage Documents

ABSTRACT

Unstructured explanatory information is added to an electronic mortgage form and other borrower/applicant documentation. When a user wishes to document or explain any entry or data, the user may add and insert an explanatory footnote into the electronic mortgage form and other borrower/applicant documentation. The user may enter a keyboard command or other instruction for locating and formatting the footnote. The user enters/types the text of the footnote, which may also include or specify an HTML tag that references a document attachment. When the electronic mortgage form is then generated, the electronic mortgage form incorporates the explanatory footnote. However, the HTML tag is replaced with a more human-understandable attachment name.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims domestic benefit of U.S. Provisional ApplicationNo. 62/771,620 filed Nov. 27, 2018 and incorporated herein by referencein its entirety.

BACKGROUND

Standardization of processes and data is one of the benefits that usersgain from business application software. Data is structured and as suchput into databases and other structured storage, from where it can beretrieved easily and which allows for methodically analyzing it. Oftensuch data will be used to populate forms which themselves represent datain a structured manner.

An example of such a form would be a financial assessment of a mortgageapplicant.

While most data is available in a measurable and often numeric value,there may be additional explanatory information that might be relevantfor a credit decision (in the case of a mortgage application). Forinstance, a drop in the FICO score might have an explanation, such as amedical incident or fraud committed by a third party. Additionally,there might be supporting documentation. While some of these cases canbe anticipated, and built into the system and into the forms that areused to collect and report the information, there will always be theoccasional request that unformatted context needs to be collected andstored. Often such information then has to populate well-defined paperforms, that don't have space for explanations in the particularlocations of the form, where such explanations would be most helpful.

Current systems do not allow to systematically handle such situations.This is particularly the case when data is electronically stored instructured storage, such as databases and then such data is reproducedinto well defined forms. State of the art is to allow for a generalcomment that handles the whole data-set or form.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The features, aspects, and advantages of the exemplary embodiments areunderstood when the following Detailed Description is read withreference to the accompanying drawings, wherein:

FIG. 1 is a simplified illustration of an operating environment,according to exemplary embodiments;

FIGS. 2-5 are examples of a graphical user interface, according toexemplary embodiments; and

FIG. 6 illustrates an electronic database, according to exemplaryembodiments.

DETAILED DESCRIPTION

The exemplary embodiments will now be described more fully hereinafterwith reference to the accompanying drawings. The exemplary embodimentsmay, however, be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Theseembodiments are provided so that this disclosure will be thorough andcomplete and will fully convey the exemplary embodiments to those ofordinary skill in the art. Moreover, all statements herein recitingembodiments, as well as specific examples thereof, are intended toencompass both structural and functional equivalents thereof.Additionally, it is intended that such equivalents include bothcurrently known equivalents as well as equivalents developed in thefuture (i.e., any elements developed that perform the same function,regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill inthe art that the diagrams, schematics, illustrations, and the likerepresent conceptual views or processes illustrating the exemplaryembodiments. The functions of the various elements shown in the figuresmay be provided through the use of dedicated hardware as well ashardware capable of executing associated software. Those of ordinaryskill in the art further understand that the exemplary hardware,software, processes, methods, and/or operating systems described hereinare for illustrative purposes and, thus, are not intended to be limitedto any particular named manufacturer.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless expressly stated otherwise. Itwill be further understood that the terms “includes,” “comprises,”“including,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. It will be understood thatwhen an element is referred to as being “connected” or “coupled” toanother element, it can be directly connected or coupled to the otherelement or intervening elements may be present. Furthermore, “connected”or “coupled” as used herein may include wirelessly connected or coupled.As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first device could be termed asecond device, and, similarly, a second device could be termed a firstdevice without departing from the teachings of the disclosure.

FIG. 1 is a simplified illustration of an operating environment,according to exemplary embodiments. A server 20 communicates with aclient device 22 via a communications network 24. FIG. 1 illustrates theclient device 22 as a mobile tablet computer 26, which most readers arethought familiar. The client device 22, however, may be a server, mobilesmartphone, computer, or any other processor-controlled device, as laterparagraphs will explain. Regardless, the client device 22 sends anelectronic request 28 via the communications network 24 to a networkaddress (e.g., Internet protocol address) associated with the server 20.The electronic request 28 requests an electronic document 30 andspecifies a query parameter 32. While the electronic document 30 mayrepresent or contain any information or data, most readers are alsothought familiar with an electronic mortgage application 34. That is,the electronic request 28 may request electronic data, database entries,forms, and/or documents that are related to the electronic mortgageapplication 34. A user may thus instruct or cause the mobile tabletcomputer 26 to send the electronic request 28 specifying the queryparameter 32. When the server 20 receives the electronic request 28, theserver 20 queries an electronic database 36 for the query parameter 32specified by the electronic request 28.

The server 20 retrieves information stored in the electronic database36. The server 20 has a processor 38 that executes a server-sideapplication 40 stored in a solid-state memory device 42. The mobiletablet computer 26 has a processor 44 that executes a client-sideapplication 46 stored in a solid-state memory device 48. The server-sideapplication 40 and the client-side application 46 may thus cooperate(perhaps in a client-server relationship) to identify and/or to retrieveelectronic mortgage data 50, database entries 52, mortgage forms 54,and/or other information stored in the electronic database 36 that isrelated to the electronic mortgage application 34. For example, theserver-side application 34 instructs or causes the processor 38 to reador inspect the electronic request 28 for the query parameter 32. Theserver-side application 34 instructs or causes the processor 38 to querythe electronic database 36 for the query parameter 32 and identify itscorresponding electronic mortgage data 50, database entries 52, mortgageforms 54, and/or other information that is related to the electronicmortgage application 34. The server-side application 34 may theninstruct or cause the processor 38 to retrieve any data or informationcontained within and/or referenced by the electronic database 36. Theserver-side application 34 may even instruct or cause the processor 38to assemble or to arrange the electronic mortgage data 50 and/or thedatabase entries 52 as the mortgage forms 54. Regardless, the server 20sends a query response 56 to the network address (e.g., Internetprotocol address) associated with the mobile tablet computer 26.

The mobile tablet computer 26 receives the query response 56. The queryresponse 56 may be sent as one or more packetized messages 58, web pages60, or short message service (SMS) messages 62. The query response 56may additionally or alternatively be posted to a social network.Regardless, the query response 56 may contain the electronic mortgagedata 50, the database entries 52, and/or the mortgage forms 54 that arerelated to the query parameter 32 specified by the electronic request28. The query response 56 may also contain or reference a hyperlink 64that permits the mobile tablet computer 26 to download data orinformation identified by the electronic database 36. When the mobiletablet computer 26 receives the query response 56, the client-sideapplication 34 instructs or causes its processor 44 to present the queryresponse 56 to the user. The tablet computer 26, for example, maygenerate a graphical user interface (or GUI) 66 or display by itsdisplay device 68. The graphical user interface 66 incorporates the dataor information identified by the electronic database 36 (e.g., theelectronic mortgage data 50, the database entries 52, and/or themortgage forms 54). The tablet computer 26 thus be visually and/oraudibly presents the graphical user interface 66 to the user.

The server 20 may thus be a central or network repository. The server 20may store or maintain the electronic database 36 as a resource forrequesting clients (such as the mobile tablet computer 26). The servermay store the database entries 52 that map, relate, or associate manyconventional and reverse electronic mortgage applications 34, themortgage forms 54, and/or their corresponding and/or supportingelectronic mortgage data 50. The server 20 may thus have hundreds,thousands, or even millions of database entries 52 that map or relatedifferent users to their electronic mortgage applications 34.

FIG. 2 is an example of the graphical user interface 66, according toexemplary embodiments. The graphical user interface 66 illustrates anelectronic mortgage data record 70 that relates to an applicant'selectronic mortgage application (illustrated as reference numeral 34 inFIG. 1). The electronic mortgage data record 70 has data fields thatvisually incorporate their corresponding electronic mortgage data 50and/or the database entries 52 identified by the electronic database 36(all illustrated in FIG. 1). The electronic mortgage data record 70displays a set of current credits, each of them furthermore simplycalled credit or record (the more technical term) that are the basis fora new credit decision. Each credit consists of structured data such asName 72, Account Number 74, Balance 76, Next Payment Amount 78, LatePayments 80, and others. To each of these credits there are the standardcredit documents such as a written loan agreement, a credit cardapplication and periodic statements. Well-designed systems alsoanticipate special situations, such as joint credit accounts, stolencredit cards and provide structured ways to handle these. But there canbe situations that were not anticipated, such as a credit card issuerissued the same credit card number twice, resulting in lots ofexplanations and supporting documents.

The electronic mortgage data record 70 may have one or more categories.For example, a System Generated Identifier 82 may be one of theelectronic mortgage data 50 and/or the database entries 52 that used tolet humans distinguish the different credits in the system that areallocated to a particular case. This does not need to be the same as therecord Id that is being used for persistent storage. One or moreStructured Data fields 84 present the electronic mortgage data 50 and/orthe database entries 52 (retrieved from the electronic database 36illustrated in FIG. 1) in a structured form, such as the Name 72,Account Number 74, Balance 76, Next Payment Amount 78, Late Payments 80within a predefined period. This data is entered in well-defined fieldsthat are specific to each entry, such as the balance 76 of the account.This structured approach doesn't leave any room for entering data thatdoesn't strictly conform to the structure. Attachments 86 are documentsthat are stored electronically. The graphical user interface 66 presentsthe attachments 86 as accessed through the hyperlink 64, a graphicalcontrol button or any other access scheme. The Attachments 86 themselvescan be clearly defined such as a W9. But the Attachments 86 can also beless structured and defined, such as explanatory letters, policereports, pictures. One or more Explanations 88 allow for unstructuredexplanatory entries. This can be plain text or formatted text such asHTML, allowing to insert hyperlinks to the Attachments 86. A user of themobile tablet computer 26 may thus place a cursor and manually entertextual commentary into the field representing the Explanations 88.

FIGS. 3-4 are more examples of the graphical user interface 66,according to exemplary embodiments. The graphical user interface 66again illustrates the electronic mortgage data record 70 that relates toan applicant's electronic mortgage application (illustrated as referencenumeral 34 in FIG. 1). The graphical user interface 66 generallydisplays the same categories. A Record Id 90 is any unique identifierused in the electronic database 36 for the electronic mortgage datarecord 70 and/or an applicant's electronic mortgage application 34. AnId 92 is a system-generated identifier that allows for humanidentification of the electronic mortgage data record 70 and/or anapplicant's electronic mortgage application 34 in a list of presentedrecords. The graphical user interface 66 may also present the Name 72,Account Number 74, Balance 76, Next Payment Amount 78, and Late Payments80. All these fields should have appropriate types for the data entered.

The Attachments 86 field is also illustrated. While the attachments 86(such as pdf documents) can be stored directly inside the electronicmortgage data record 70 and/or an applicant's electronic mortgageapplication 34, best practices rather suggest alternatively storing theAttachments 86 separately, in a file system or other adequate storageand have references to the stored attachments. This alternative isachieved with an attachment class structure 94. The attachment classstructure 94 in its simplest form has two properties:

-   -   1. AttachmentName 96, a string to store the human understandable        name of the file attachment (such as “Statement from Credit Bank        of Ohio”); and    -   2. A file reference 98, which contains a unique identifier to        identify the file attachment, often this would also be the file        name.        Methods to store and retrieve files based on an identifier or        file name are well documented. In the below simple example, the        file name is simply and uniquely identified as “534.”

The Text 88 is also illustrated. The Text 88 allows a user to enterunstructured textual information. It is advantageous to use a markuplanguage such as hyper-text HTML, which allows for extensions. Thisexample will extend HTML with a tag <special-document> and allow for anattribute “sd-reference” (illustrated as reference numeral 100). TheText 88 effectively stored would then appear as

-   -   “While Credit Bank sent a letter of apology, <special-document        sd-reference:“534”>, they never removed . . . .”        The textual number “534” represents the unique file identifier        reference 98 of the attachment file 86, allowing the system        (such as the server 20 and/or the mobile tablet computer 26) to        retrieve the attachment file 86 itself as the attachment class        structure 94 and henceforth the AttachmentName 96. The user of        server 20 and/or the mobile tablet computer 26 may even access        an interface or software tool for changing the AttachmentName 96        (in this case of the attachment 86).

As FIG. 4 illustrates, exemplary embodiments may then modify and/orreplace the tag attribute “sd-reference” 100 with the humanunderstandable AttachmentName 96 so it appears as:

-   -   “While Credit Bank sent a letter of apology, Statement from        Credit Bank of Ohio, they never removed . . . .”        The hyperlinked “Statement from Credit Bank of Ohio” is a        uniform resource locator that points to the respective        Attachment 86 instance so that a simple user's mouse click or        other tactile selection can request, download, and open the        attachment document itself and show it in the respective        application (such as a pdf viewer). Referencing an attachment Id        and retrieving the name of the attachment (AttachmentName 96)        when rendering allows for changes in the name of the attachment        while keeping the text consistent.

FIG. 5 is another example of the graphical user interface 66, accordingto exemplary embodiments. The graphical user interface 66 againillustrates the electronic document 30 as multiple mortgage forms 54that incorporate the electronic mortgage data 50 and/or the databaseentries 52 identified in the electronic database 36 (illustrated in FIG.1). The graphical user interface 66 may process and include a footnote110 as the hyperlink 64 to further informational content. The server(illustrated as reference numeral 20 in FIG. 1) may store, retrieve, andsend the electronic mortgage data 50 and/or the database entries 52(illustrated in FIG. 1) that are used to generate and/or to display thefootnote 110. The graphical user interface 66 displays the mortgageforms 54 that arrange or organize the corresponding electronic mortgagedata 50 and/or the database entries 52, perhaps according to astructured and non-structured format. Many electronic forms arewell-defined and do not allow for non-structured information to bepresented. But there is always the possibility to add furtherinformation behind the formal part of the form or on a blank additionalpage.

The footnote 110 ties additional information to the correct entry in theelectronic mortgage forms 54. The footnote 110 is a humanunderstandable, electronic reference webpage hyperlink 64. The footnote110, though, is preferably encoded in a markup language such as HTMLthat allows inserting the hyperlink 64 inside the electronic mortgagedata record 70 where the user wishes to add the unstructured text 88.FIG. 5, for example, illustrates the user inserting the footnote 110(“F3”) as additional commentary for the columnar database entry “CreditBank Credit Card” (illustrated as reference numeral 112). As the readermay recognize, the “Credit Bank Credit Card” 112 corresponds to theAttachmentName 96 (previously explained with reference to FIGS. 3-4).While the footnote 110 may be added to any location within theelectronic mortgage data record 70, the reader likely understands thatthe footnote 110 is preferably inserted as textual commentary proximateto its corresponding columnar database entry 112. In order to make thefootnote 110 hyperlink human readable, the text may include a footnoteID and reference text. In this example the text reads “F3”, whereas “F”can stand for Footnote and then the number “3” references the humanunderstandable Id of the record. Thus, the hyperlink 64 may be termedhyperlink F3.

The unstructured text 88 may be added to the end of the electronicmortgage data record 70 representing the mortgage form 54. The graphicaluser interface 66, the electronic mortgage data record 70, and/or themortgage form 54 may thus be generated to include a Footnote section114. There could be multiple footnotes 110 for other records. Recordsand their corresponding footnotes 110 may be linked through a humanlyreadable reference index. For example, the footnote “F3” links the thirdrecord AttachmentName 96 (e.g., the “Credit Bank Credit Card” 112) tothe footnote number 3. Furthermore, there can be a hyperlink embeddedthrough a method called anchor. The link in hyperlink F3 in the recordwill show up as:

-   -   <a onclick=“scrolltoFootNote(‘F3’)”>F3)</a>        Whereas the footnote 110 at the end of the webpage 60, the        electronic mortgage data record 70, and/or the mortgage form 54        will be the anchor which can be encoded as:

  <div data-short-id=″F3″ class=″faw-row″>  <div class=″faw-cellbolder″> <span>F3)</span> </div>  <div class=″footnotes″> <p>(FootnoteText...)</p> </div> </div>The Attachments 86 may be made available on the server 20. In order toaccess them from within the footnote 110 (where they are referenced),the Attachments 86 may be embedded in the hyperlink 64. The reference inthe original text is then replaced with an updated hyperlink 64:

-   -   “While Credit Bank sent a letter of apology, <A        href=“https://www.url/thedocument.pdf”>Statement from Credit        Bank of Ohio</A> they never removed . . . ”        The hyperlink https://www.url/thedocument.pdf will then point to        the URL of the document that is made available on the server 20.

FIG. 6 further illustrates the electronic database 36, according toexemplary embodiments. FIG. 6 illustrates the electronic database 36 asa table 120 that electronically maps, relates, or associates theattachments 86 to their corresponding tag attribute 100, footnote 110,text 88, and/or hyperlink 64. The table 120 may thus have entriesarranged as relational columns and rows that map or relate eachdifferent footnote 110 to its corresponding constituent or componentdatabase information. The electronic database 36 is illustrated as beinglocally stored in the server 20, but some or all of the electronicdatabase entries 52 may be remotely maintained at some other server orlocation in the communications network (illustrated as reference numeral24 in FIG. 1). Although FIG. 6 only illustrates a few entries, inpractice the electronic database 36 may contain many entries that richlydetail the footnotes 110 inserted into hundreds, thousands, or millionsof the electronic mortgage data records 70 for many mortgage applicants.In practice, then, the electronic database 36 may contain many entriesthat richly detail many electronic mortgage applications 34.

Returning to FIG. 1, the server 20 may send the electronic mortgage form54 as the query response 56 to the electronic request 26. Once theserver 20 determines the attachment 86 and its corresponding tagattribute 100, footnote 110, text 88, and/or hyperlink 64, the server 20may generate the electronic mortgage form 54. The electronic mortgageform 54 incorporates the footnote 110 and its explanatory text 88. Thefootnote 110 may further incorporate the hyperlink 64 to permit mousingover or other tactile selection to download and view the attachment 86.The electronic mortgage form 54 may be generated as or formatted as thepacketized messages 58, web pages 60, or short message service (SMS)messages 62.

Exemplary embodiments may utilize any processor-controlled device, suchas the above-mentioned server 20 and/or tablet computer 26. However, theprocessor-controlled device may be a tablet computer, tablet, digitalwatch, digital media player, digital television, or any other devicehaving a processor and solid-state memory device. Theprocessor-controlled device has a network interface to thecommunications network 24, thus allowing two-way, bidirectionalcommunication with clients, servers, and other network-accessibledevices. The server-side application 40 and the client-side application46 include instructions, code, and/or programs that cause theprocessor-controlled device to perform operations, such ascalling/retrieving any of the electronic mortgage data 50 or entries 52in the electronic database 26 and generating the mortgage form 54 and/orthe electronic mortgage data record 70. The electronic database 36 mayfurther have tabular (e.g., columns and rows) entries that further mapor associate any of the Name 72, Account Number 74, Balance 76, NextPayment Amount 78, and Late Payments 80, system generated identifier 82,Record Id 90, and/or Id 92 to their corresponding attachments 86, and totheir corresponding tag attribute 100, footnote 110, text 88, and/orhyperlink 64. Any of the entries in the electronic database may beidentified and/or retrieved and sent as a packetized message via thecommunications network to any other device or network address (e.g.,Internet protocol address). The processor-controlled device may thusaccept or receive queries from clients, and each query specifies a queryparameter. If the electronic database contains or references asatisfying or matching entry, any related entries may be identified andsend as a query response to the client.

Exemplary embodiments may be applied regardless of networkingenvironment. Exemplary embodiments may be easily adapted to stationaryor mobile devices having cellular, wireless fidelity (WI-FI®), nearfield, and/or BLUETOOTH® capability. Exemplary embodiments may beapplied to mobile devices utilizing any portion of the electromagneticspectrum and any signaling standard (such as the IEEE 802 family ofstandards, GSM/CDMA/TDMA or any cellular standard, and/or the ISM band).Exemplary embodiments, however, may be applied to anyprocessor-controlled device operating in the radio-frequency domainand/or the Internet Protocol (IP) domain. Exemplary embodiments may beapplied to any processor-controlled device utilizing a distributedcomputing network, such as the Internet (sometimes alternatively knownas the “World Wide Web”), an intranet, a local-area network (LAN),and/or a wide-area network (WAN). Exemplary embodiments may be appliedto any processor-controlled device utilizing power line technologies, inwhich signals are communicated via electrical wiring. Indeed, exemplaryembodiments may be applied regardless of physical componentry, physicalconfiguration, or communications standard(s).

Exemplary embodiments may utilize any processing component,configuration, or system. Any processor could be multiple processors,which could include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The processor could includea state machine, application specific integrated circuit (ASIC),programmable gate array (PGA) including a Field PGA, or state machine.When any of the processors execute instructions to perform “operations,”this could include the processor performing the operations directlyand/or facilitating, directing, or cooperating with another device orcomponent to perform the operations.

Exemplary embodiments may packetize. When the processor-controlleddevice communicates via the communications network, theprocessor-controlled device may collect, send, and retrieve information.The information may be formatted or generated as packets of dataaccording to a packet protocol (such as the Internet Protocol). Thepackets of data contain bits or bytes of data describing the contents,or payload, of a message. A header of each packet of data may containrouting information identifying an origination address and/or adestination address.

Exemplary embodiments may be physically embodied on or in acomputer-readable memory device or other storage medium. Thiscomputer-readable medium, for example, may include CD-ROM, DVD, tape,cassette, floppy disk, optical disk, memory card, memory drive, andlarge-capacity disks. This computer-readable medium, or media, could bedistributed to end-subscribers, licensees, and assignees. A computerprogram product comprises processor-executable instructions for addingfootnotes to electronic mortgage documents, as the above paragraphsexplained.

While the exemplary embodiments have been described with respect tovarious features, aspects, and embodiments, those skilled and unskilledin the art will recognize the exemplary embodiments are not so limited.Other variations, modifications, and alternative embodiments may be madewithout departing from the spirit and scope of the exemplaryembodiments.

1. A system, comprising: a hardware processor; and a memory device, thememory device storing instructions, the instructions when executedcausing the hardware processor to perform operations, the operationscomprising: receiving a query sent from a client device, the queryrequesting an electronic mortgage form and specifying a query parameter;querying an electronic database for the query parameter specified by thequery sent from the client device, the electronic databaseelectronically associating attachment class structures to footnotes andto hyperlinks associated with electronic mortgage forms; identifying anattachment class structure of the attachment class structures in theelectronic database that is electronically associated with the queryparameter specified by the query sent from the client device;identifying a footnote of the footnotes in the electronic database thatis electronically associated with the query parameter specified by thequery sent from the client device; identifying a hyperlink of thehyperlinks in the electronic database that is electronically associatedwith the query parameter specified by the query sent from the clientdevice; generating the electronic mortgage form as a query response tothe query sent from the client device, the electronic mortgage formincorporating the hyperlink into the footnote to download an attachmentrepresented by the attachment class structure; and sending theelectronic mortgage form as the query response to the query sent fromthe client device.
 2. The system of claim 1, wherein the operationsfurther comprise identifying explanatory text in the electronic databasethat is electronically associated with the query parameter specified bythe query sent from the client device.
 3. The system of claim 2, whereinthe operations further comprise generating the electronic mortgage formincorporating the explanatory text into the footnote as a textualexplanation of the attachment.
 4. The system of claim 2, wherein theoperations further comprise identifying a hypertext markup language tagin the electronic database that is electronically associated with thequery parameter specified by the query sent from the client device. 5.The system of claim 4, wherein the operations further comprisegenerating the electronic mortgage form incorporating the hypertextmarkup language tag into the footnote as a textual explanation of theattachment.
 6. The system of claim 1, wherein the operations furthercomprise identifying explanatory text in the electronic database that iselectronically associated with the query parameter specified by thequery sent from the client device.
 7. The system of claim 6, wherein theoperations further comprise identifying a hypertext markup language tagin the explanatory text.
 8. The system of claim 7, wherein theoperations further comprise replacing the hypertext markup language tagin the explanatory text with the attachment class structure identifiedin the electronic database.
 9. A method, comprising: receiving, by aserver, a query sent from a client device, the query requesting anelectronic mortgage form and specifying a query parameter; querying, bythe server, an electronic database for the query parameter specified bythe query sent from the client device, the electronic databaseelectronically associating attachment class structures to footnotes andhyperlinks associated with electronic mortgage forms; identifying, bythe server, an attachment name of the attachment class structures in theelectronic database that is electronically associated with the queryparameter specified by the query sent from the client device;identifying, by the server, a footnote of the footnotes in theelectronic database that is electronically associated with the queryparameter specified by the query sent from the client device;identifying, by the server, a hyperlink of the hyperlinks in theelectronic database that is electronically associated with the queryparameter specified by the query sent from the client device;generating, by the server, the electronic mortgage form as a queryresponse to the query sent from the client device, the electronicmortgage form incorporating the attachment name into the footnote todownload an attachment represented by the hyperlink; and sending, by theserver, the electronic mortgage form as the query response to the querysent from the client device.
 10. The method of claim 9, furthercomprising identifying explanatory text in the electronic database thatis electronically associated with the query parameter specified by thequery sent from the client device.
 11. The method of claim 10, furthercomprising generating the electronic mortgage form incorporating theexplanatory text into the footnote as a textual explanation of theattachment.
 12. The method of claim 10, further comprising identifying ahypertext markup language tag in the electronic database that iselectronically associated with the query parameter specified by thequery sent from the client device.
 13. The method of claim 12, furthercomprising generating the electronic mortgage form incorporating thehypertext markup language tag into the footnote as a textual explanationof the attachment.
 14. The method of claim 9, further comprisingidentifying explanatory text in the electronic database that iselectronically associated with the footnote.
 15. The method of claim 14,further comprising identifying a hypertext markup language tag in theexplanatory text.
 16. The method of claim 15, further comprisingreplacing the hypertext markup language tag in the explanatory text withthe attachment name identified in the electronic database.
 17. A memorydevice storing instructions that when executed cause a hardwareprocessor to perform operations, the operations comprising: receiving aquery sent from a client device, the query requesting an electronicmortgage form and specifying a query parameter; querying an electronicdatabase for the query parameter specified by the query sent from theclient device, the electronic database electronically associatingattachment class structures to footnotes and hyperlinks associated withelectronic mortgage forms; identifying an attachment name of theattachment class structures in the electronic database that iselectronically associated with the query parameter specified by thequery sent from the client device; identifying a footnote of thefootnotes in the electronic database that is electronically associatedwith the query parameter specified by the query sent from the clientdevice; identifying a hyperlink of the hyperlinks in the electronicdatabase that is electronically associated with the query parameterspecified by the query sent from the client device; generating theelectronic mortgage form as a query response to the query sent from theclient device, the electronic mortgage form incorporating the attachmentname into the footnote to download an attachment represented by thehyperlink; and sending the electronic mortgage form as the queryresponse to the query sent from the client device.
 18. The memory deviceof claim 17, wherein the operations further comprise identifyingexplanatory text in the electronic database that is electronicallyassociated with the footnote.
 19. The memory device of claim 18, whereinthe operations further comprise identifying a hypertext markup languagetag in the explanatory text.
 20. The memory device of claim 17, whereinthe operations further comprise replacing the hypertext markup languagetag in the explanatory text with the attachment name identified in theelectronic database.